Microservices Architecture by Ajay Kumar

Author:Ajay Kumar [Kumar, Ajay]
Language: eng
Format: azw3
Publisher: UNKNOWN
Published: 2018-04-21T16:00:00+00:00

Approach: Automation

➢ Continuous Integration Tools

■ Work with source control systems ■ Automatic after check-in ■ Unit tests and integration tests required ■ Ensure quality of check-in

● Code compiles

● Tests pass

● Changes integrate

● Quick feedback

■ Urgency to fix quickly

■ Creation of build

■ Build ready for test team

■ Build ready for deployment

Automation: CI Tools

Another key design principle for microservices architecture is automation. One aspect of automation in the microservices context is the use of tools to provide automatic testing and feedback for software changes. These tools are normally known as Continuous Integration Tools, and these Continuous Integration Tools basically work with our source control system. They automatically test our software after we check-in and change to the software into the source control system where they test our software by basically running unit tests and integration tests that we've written. Unit tests and integration tests are basically bits of code which is designed to test our production code. They basically test that a change or enhancement in the code doesn't break any of the existing requirements. So in order to fully benefit from using continuous integration tools, unit tests and integration tests should be implemented, so continuous integration tools basically allow us to ensure that our code compiles, and that our tests pass, and that our changed software integrates with anything else that might use our software, and these tools also provide us with quick feedback. So if a change to a microservice breaks the microservice itself, or breaks anything else which might use a microservice, the Continuous Integration Tool will give us quick feedback so that we can fix the issue quickly. So in a microservices system with so many moving parts, this kind of information on the quality of integration is super useful. Quick feedback also causes an urgency to fix things quickly and issues don't pile up, because automatic feedback is sent to the team and then can quickly address the issue. In fact, the team culture should be to stop any development until all issues reported by the Continuous Integration Tool have been fixed. The continuous integration tool can also be used to build our software as part of the test, and this build can be used by the test team to test the software, and it can also be used for deployment. In the next section of the module, we'll look at how deployment tools can be used to take builds created by the Continuous Integration Tools and have them deployed automatically.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.